Skip to content

CS-343 [New Framework] - PIPEDA, CS-333 [New Framework] - CCPA#2759

Merged
Marfuen merged 15 commits into
mainfrom
chas/add-PIPEDA-CCPA
May 7, 2026
Merged

CS-343 [New Framework] - PIPEDA, CS-333 [New Framework] - CCPA#2759
Marfuen merged 15 commits into
mainfrom
chas/add-PIPEDA-CCPA

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 6, 2026

This is an automated pull request to merge chas/add-PIPEDA-CCPA into dev.
It was created by the [Auto Pull Request] action.


Summary by cubic

Adds PIPEDA and CCPA as first-class frameworks across the Trust Center and public trust portal (Linear CS-343, CS-333). Users can toggle them, set status (incl. in-progress), upload/preview certificates, and see badges/logos.

  • New Features

    • Database: added pipeda, pipeda_status, ccpa, ccpa_status to Trust and extended TrustFramework with pipeda/ccpa (migrations included).
    • API: updated trust-portal.service and trust-access.service to read/write PIPEDA/CCPA booleans and statuses, accept camelCase/snake_case, include them in settings payloads, and expose badge/label mappings.
    • App: added PIPEDA/CCPA toggles and status controls in portal settings with new logos and in-progress variants, certificate upload/preview support, and badge SVGs (/badges/pipeda.svg, /badges/ccpa.svg) shown in Frameworks Overview/Table. Trust page now passes PIPEDA/CCPA flags, statuses, and certificate filenames.
  • Migration

    • Apply the latest Prisma migrations for new columns and enum values, then regenerate the Prisma client and redeploy.

Written for commit ff0ef54. Summary will update on new commits.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Ready Ready Preview, Comment May 7, 2026 4:51pm
comp-framework-editor Ready Ready Preview, Comment May 7, 2026 4:51pm
portal Ready Ready Preview, Comment May 7, 2026 4:51pm

Request Review

@chasprowebdev chasprowebdev changed the title [dev] [chasprowebdev] chas/add-PIPEDA-CCPA CS-343 [New Framework] - PIPEDA, CS-333 [New Framework] - CCPA May 6, 2026
@linear
Copy link
Copy Markdown

linear Bot commented May 6, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 11 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

@chasprowebdev
Copy link
Copy Markdown
Contributor

@cubic-dev-ai please review this.

@cubic-dev-ai
Copy link
Copy Markdown
Contributor

cubic-dev-ai Bot commented May 6, 2026

@cubic-dev-ai please review this.

@chasprowebdev I have started the AI code review. It will take a few minutes to complete.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 11 files

Confidence score: 3/5

  • There is a concrete functional risk: packages/db/prisma/schema/trust.prisma adds PIPEDA/CCPA on Trust, but TrustFramework was not updated to match, which can block certificate persistence in TrustResource for those frameworks.
  • Given the high severity/confidence signal (7/10, 9/10), this is more than a housekeeping mismatch and could produce user-facing gaps when handling new trust frameworks.
  • Pay close attention to packages/db/prisma/schema/trust.prisma - enum/model alignment is needed so new frameworks can be stored consistently.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/db/prisma/schema/trust.prisma">

<violation number="1" location="packages/db/prisma/schema/trust.prisma:28">
P1: PIPEDA/CCPA were added on `Trust`, but `TrustFramework` was not extended, so TrustResource cannot store certificate entries for these new frameworks.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.

Comment thread packages/db/prisma/schema/trust.prisma
@chasprowebdev
Copy link
Copy Markdown
Contributor

Screenshot 2026-05-06 at 9 25 32 AM Screenshot 2026-05-06 at 9 25 55 AM Screenshot 2026-05-06 at 9 26 22 AM

@chasprowebdev chasprowebdev requested review from Marfuen and tofikwest May 6, 2026 13:29
@chasprowebdev
Copy link
Copy Markdown
Contributor

@cubic-dev-ai please review this.

@cubic-dev-ai
Copy link
Copy Markdown
Contributor

cubic-dev-ai Bot commented May 7, 2026

@cubic-dev-ai please review this.

@chasprowebdev I have started the AI code review. It will take a few minutes to complete.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 12 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

@Marfuen Marfuen merged commit 1b62b52 into main May 7, 2026
11 checks passed
@Marfuen Marfuen deleted the chas/add-PIPEDA-CCPA branch May 7, 2026 17:29
@claudfuen
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.47.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants